

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>M [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Glossary,Glossary M">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <div style="text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;"><table cellspacing="0" cellpadding="0" border="0" style="border: none; border-spacing:0px;">
<tr style="text-align:left;vertical-align:top;">
<td valign="middle" width="38" style="width:38px;"><p class="p_Heading1"><a href="glossaryofterms.htm"><img src="glossary%20page.gif" width="29" height="29" border="0" alt="Glossary Page"></a></p>
</td>
<td valign="middle" width="608" style="width:608px;"><p class="p_Heading1"><span class="f_Heading1">~M~</span></p>
</td>
</tr>
</table>
</div>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="l(glossary).htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="n(glossary).htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_Glossaryitem"><span class="f_Glossaryitem">maintenance</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The support of a software system after it is deployed.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">manifest</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A relationship that indicates that the artifact source embodies the target model element. Stereotypes can be added to Enterprise Architect to classify the type of manifestation of the model element.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">message</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">Messages indicate a flow of information, or transition of control, between elements. Messages are used by Communication diagrams, Sequence diagrams, Interaction Overview diagrams and Timing diagrams.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">message endpoint</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">An element that defines an endpoint of a Lifeline, such as a State or Value Lifeline in a Timing diagram.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">message label</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">Used for messages sent between Lifelines to make the diagram appear less cluttered. Labels with the same name indicate that a message can be interrupted.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">metaclass</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A Class whose instances are Classes. Metaclasses are typically used to construct metamodels.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">metafile</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A vector-based image format native to Windows. Supports high detail and excellent scaling. Typically used for saving diagram images for placement in documents. Comes in Placeable (an older format) and Enhanced (current standard format).</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">meta-metamodel</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A model that defines the language for expressing a metamodel. The relationship between a meta-metamodel and a metamodel is analogous to the relationship between a metamodel and a model.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">metamodel</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A model that defines the language for expressing a model.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">meta-object</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A generic term for all meta-entities in a meta-modeling language. For example, meta-types, meta-classes, meta-attributes, and meta-associations.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">Meta-Object Facility (MOF)</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">An Object Management Group (OMG) standard. MOF originated in the UML, when the OMG required a Meta-Modeling architecture to define the UML. MOF is designed as a four-layered architecture.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">method</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The implementation of an operation. It specifies the algorithm or procedure associated with an operation.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">model [MOF]</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">An abstraction of a physical system with a certain purpose.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also: </span><span class="f_Glossarytext">physical system</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Usage note:</span><span class="f_Glossarytext"> In the context of the MOF specification, which describes a meta-metamodel, the meta-metamodel is for brevity frequently referred to simply as the model.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">model aspect</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A dimension of modeling that emphasizes particular qualities of the metamodel. For example, the structural model aspect emphasizes the structural qualities of the metamodel.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">model elaboration</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The process of generating a repository type from a published model. Includes the generation of interfaces and implementations which enables repositories to be instantiated and populated based on, and in compliance with, the model elaborated.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">model element [MOF]</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">An element that is an abstraction drawn from the system being modeled.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Contrast</span><span class="f_Glossarytext">:</span><span class="f_Glossarytext"> view element; in the MOF specification model elements are considered to be meta-objects.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">model library</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A stereotyped package containing model elements that are intended to be reused by other packages. A model library differs from a profile in that a model library does not extend the metamodel using stereotypes and tagged definitions. A model library is analogous to a Class library in some programming languages.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">modeling time</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">Refers to something that occurs during the modeling phase of the software development process. It includes analysis time and design time.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Usage note</span><span class="f_Glossarytext">: When discussing object systems, it is often important to distinguish between modeling-time and run-time concerns.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also:</span><span class="f_Glossarytext"> analysis time, design time, compile time</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Contrast:</span><span class="f_Glossarytext"> run time</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">module</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A software unit of storage and manipulation. Modules include source code modules, binary code modules and executable code modules.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also:</span><span class="f_Glossarytext"> component</span></p>
<p><span class="f_Glossaryitem">MOF</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">Meta-Object Facility, an Object Management Group (OMG) standard. MOF originated in the UML, when the OMG required a Meta-Modeling architecture to define the UML. MOF is designed as a four-layered architecture.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">multiple classification</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A semantic variation of Generalization in which an object can belong directly to more than one classifier.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also: </span><span class="f_Glossarytext">static classification, dynamic classification</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">multiple inheritance</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A semantic variation of Generalization in which a type can have more than one supertype.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Contrast: </span><span class="f_Glossarytext">single inheritance</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">multiplicity</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A specification of the range of enableable cardinalities that a set can assume. Multiplicity specifications can be given for roles within Associations, Parts within Composites, repetitions and other purposes. Essentially a multiplicity is a (possibly infinite) subset of the non-negative integers.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Contrast:</span><span class="f_Glossarytext"> cardinality</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">multi-valued [MOF]</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A model element with multiplicity defined whose </span><span class="f_Glossarytext" style="font-style: italic;">Multiplicity Type::</span><span class="f_Glossarytext"> upper attribute is set to a number greater than one. The term multi-valued does not pertain to the number of values held by, for example, an attribute or parameter, at any point in time.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">Contrast: </span><span class="f_Glossarytext">single-valued</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
